Skip to content

feat: improve skill scores for linear-cli#173

Open
popey wants to merge 1 commit intoschpet:mainfrom
popey:improve/skill-review-optimization
Open

feat: improve skill scores for linear-cli#173
popey wants to merge 1 commit intoschpet:mainfrom
popey:improve/skill-review-optimization

Conversation

@popey
Copy link

@popey popey commented Mar 12, 2026

Hullo @schpet 👋 - I'm also a massive Linear (and their API) user, and only just discovered this tool, so thanks for making it!

I ran your skills through tessl skill review at work and found some targeted improvements. Here's the before/after:

Skill Before After Change
linear-cli 54% 100% +46%
release 0% 100% +100%
Changes made

linear-cli skill (skills/linear-cli/SKILL.md + SKILL.template.md):

  • Expanded frontmatter description with specific actions (create, update, list, search, close), explicit "Use when..." trigger clause, and natural user phrases like "create a Linear issue", "list my tickets", "add a comment on ENG-123"
  • Condensed the "Why use file-based flags" explanation from a 4-bullet list to a single line — the example already demonstrates the point
  • Note: since SKILL.md is auto-generated from SKILL.template.md, both files were updated to stay in sync. You'll want to apply similar changes to the template so they persist through deno task generate-skill-docs runs

release skill (.claude/skills/release/SKILL.md):

  • Fixed name: Releasename: release (validation requires lowercase with hyphens only)
  • Removed version: 0.1.0 from frontmatter (unknown key that triggered a validation warning)
  • Rewrote description with specific actions and "Use when..." trigger clause
  • Removed redundant "When to Use" and "Prerequisites" sections (already covered by the description and discoverable by the agent)
  • Consolidated "Important Notes" into the skill header where they're immediately visible
  • Removed "Post-Release" section (generic verification steps the agent can handle)

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @popey - if you hit any snags.

Thanks in advance 🙏

Hullo @schpet 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| linear-cli | 54% | 100% | +46% |
| release | 0% | 100% | +100% |

<details>
<summary>Changes made</summary>

**linear-cli skill** (`skills/linear-cli/SKILL.md` + `SKILL.template.md`):
- Expanded frontmatter description with specific actions (create, update, list, search, close), explicit "Use when..." trigger clause, and natural user phrases like "create a Linear issue", "list my tickets", "add a comment on ENG-123"
- Condensed the "Why use file-based flags" explanation from a 4-bullet list to a single line — the example already demonstrates the point
- Note: since `SKILL.md` is auto-generated from `SKILL.template.md`, both files were updated to stay in sync. You'll want to apply similar changes to the template so they persist through `deno task generate-skill-docs` runs

**release skill** (`.claude/skills/release/SKILL.md`):
- Fixed `name: Release` → `name: release` (validation requires lowercase with hyphens only)
- Removed `version: 0.1.0` from frontmatter (unknown key that triggered a validation warning)
- Rewrote description with specific actions and "Use when..." trigger clause
- Removed redundant "When to Use" and "Prerequisites" sections (already covered by the description and discoverable by the agent)
- Consolidated "Important Notes" into the skill header where they're immediately visible
- Removed "Post-Release" section (generic verification steps the agent can handle)

</details>

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@schpet
Copy link
Owner

schpet commented Mar 12, 2026

@popey i'm interested in improving this skill, it falls apart all over the place. would you be up for running some evals for me that improve it? common things i observe: the skill wont be invoked when i mention linear, it will take a guess at the cli args which will be incorrect (such as issue show instead of issue view) or a really common one i find is it'll botch adding comments to an issue.

so, if you're up for it, i think this would be a welcome improvement but as is this PR isn't that convincing (i.e. it updates my release skill, i am the only user of that and it doesn't need changing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants